Since the automatic build and push of the docs happen on push to main and cannot be seen here, I tested it on my fork and it looks like this: https://github.com/sechkova/ml-conversational-analytic-tool/commits/main Also it needs actual changes to a "*.py" file to be triggered.

This repository could have more restrictions however and the push could fail. Also signing the commit with a GPG key (-S) is not possible by a GH Action as far as I can tell (it is possible by creating a gpg key for this purpose but not in a trivial way).

just as a reminder, after the PR is merged, we would have to enable github pages for the repo.

I checked the repo setting and we do require signed commits. Could you test out what happens if you enable a signed commit requirement for your forked repo and test out what happens with the workflow there?

I checked the repo setting and we do require signed commits. Could you test out what happens if you enable a signed commit requirement for your forked repo and test out what happens with the workflow there?

@annajung I guess as expected, the commit is declined.

remote: error: Commits must have valid signatures.

If we want to move forward the idea of an automatic commit, I'll check if it is possible to sign it in a GH Action. I'm not sure who should be the GPG key "owner" though.

Here is the full log:

Run git config --global user.name 'GitHub Actions'
[13](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:13)
[main 5c4d9e3] Build docs
[14](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:14)
 1 file changed, 4 insertions(+), 1 deletion(-)
[16](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:16)
remote: error: GH006: Protected branch update failed for refs/heads/main.        
[17](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:17)
remote: error: Commits must have valid signatures.        
[18](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:18)
To https://github.com/sechkova/ml-conversational-analytic-tool
[19](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:19)
 ! [remote rejected] main -> main (protected branch hook declined)
[20](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:20)
error: failed to push some refs to 'https://github.com/sechkova/ml-conversational-analytic-tool'
[21](https://github.com/sechkova/ml-conversational-analytic-tool/runs/5662812744?check_suite_focus=true#step:6:21)
Error: Process completed with exit code 1.

After checking the potential solututions, trying to surpass the brach protections tules by finding a way for a bot to sign the commits and sharing GPG keys as secrets sounds like an overkill for mcat, and also maybe raises some concerns.

I have this new idea, I modified the workflow to only check for uncommitted changes after building the docs and fail. This way there is a visible mark in the PR of a failure and the PR author can rebuild and commit the docs before merging.

@annajung what do you think?

Closing to clean up for deprecation